Health Cloud Financial System API - Implementation Template

Please review the pre-requisite setup instructions for setting up Salesforce Health Cloud and Salesforce Connected App.

Importing Templates into Anypoint Studio

1. In Studio, click the Exchange X icon in the upper left of the taskbar.
2. Log in with your Anypoint Platform credentials.
3. Search for the template.
4. Click Open.

Running Templates in Anypoint Studio

After you import your template into Studio, follow these configuration steps to run it:

Salesforce Health Cloud Configuration

MuleSoft's Salesforce Connector requires a username, password, and optionally a security token to communicate with Salesforce. After obtaining the necessary credentials information, configure it in the properties file located in the config/properties folder.

mule.env is the environment where the application is to be deployed. For a studio deployment, the recommended mule.env value is local.

salesforce.username should be configured in config-<mule.env>.yaml file.

salesforce.consumerKey should be configured in config-<mule.env>.yaml file.

salesforce.password should be encrypted and configured in config-secured-<mule.env>.yaml file.

salesforce.securityToken should be encrypted and configured in config-secured-<mule.env>.yaml file.

salesforce.consumerSecret should be encrypted and configured in config-secured-<mule.env>.yaml file.

Please refer to the attached link on how to secure the configuration properties.

Note: This implementation template requires Salesforce API version 52 and later.

CovergeBenefit CoverageType Picklist Setup

The following values need to be configured in Salesforce so that the proper coverage
types can be set. After logging into Salesforce in the upper right corner click the
gear icon and then select Setup. This will open the setup app. Click on the
Object Manager tab and in the Quick Find search enter Coverage Benefit. Select
Coverage Benefit from the list. Next click Fields & Relationships and click
Coverage Type. In the Coverage Type Picklist Values click the New button and
add any from this list that are missing each on their own line. Lastly click Save
to save them.

HTTPS Configuration

• https.host — sets the service host interface. It should be configured in config-<mule.env>.yaml file. (Defaults to 0.0.0.0 for all interfaces).
• https.port — sets the HTTPS service port number. It should be configured in config-<mule.env>.yaml file (Default 8082).
• TLS Configuration - Keystore properties setup:
  • keystore.alias - sets the alias to the keystore. It should be configured in config-<mule.env>.yaml file.
  • keystore.path - sets the path to the key file. Key should be available in /src/main/resources/keystore. It should be configured in config-<mule.env>.yaml file.
  • keystore.keypass — sets keystore keypass to support HTTPS operation. It should be encrypted and configured in config-secured-<mule.env>.yaml file.
  • keystore.password— sets keystore password to support HTTPS operation. It should be encrypted and configured in config-secured-<mule.env>.yaml file.

Please refer to the attached link on how to generate the Keystore.

Tested and verified

This solution was developed and tested on Anypoint Studio 7.15 and Mule Runtime 4.4.0.

Run it

• Right-click the template project folder.
• Hover your mouse over Run as.
• Click Mule Application (configure).
• Inside the dialog, select Environment and set the variable mule.env to the appropriate value (e.g dev or local).
• Inside the dialog, select Environment and set the variable mule.key to the property encryption key that you used to encrypt your secure properties. Click Run.

Deployment instructions for CloudHub using provided scripts

Ensure the Maven profile CloudHub-DEV has been properly configured in your settings.xml file. Reference can be found by downloading the Accelerator Common Resources asset. Additional instructions are available in the Getting Started with MuleSoft Accelerators - Build Environment guide.

Update the config-.yaml properties appropriately and then use one of the following scripts to deploy the application to CloudHub:

• packageDeploy.sh or deployOnly.sh (Mac/Linux)
• packageDeploy.cmd or deployOnly.cmd (Windows)

Test the template

• Use Advanced Rest Client or Postman to send a request over HTTPS. The template includes a postman collection in the src/test/resources folder. Update the collection variable(s) after successful import.